I appear to have got my JEmplode terminally confused.

It started when I was accidentally using emptool behind its back. When I realised, I reverted Jemplode's changes, but now I get a message every time I connect (pic attached). It reads "Inconsistency in playlist database. pos = 7098 but buffer.length = 7140" When I acknowledge this, it rebuilds the player database, then displays the message again, along with "<n> errors in database - check Unattached Items". After the second time, I'm in JEmplode, but all my recently-added tunes are in the wrong playlists. Unattached Items is empty.

emptool shows everything in its correct playlist. I removed a couple of orphaned playlists (by deleting the files from /drive0/fids/ and rebuilding with emptool) and still JEmplode fails.

I tried both the official (20020213) and alpha (20020304) versions of JE; no difference?

What can I do to mend JEmplode?

Later tonight I'll add some debug statements and you can grab the jar to try it out ... Unfortunately I've never seen the error you're getting, so I don't know what to tell you till I take a closer look at exactly what is coming out of your Player.

Incidentally was is <n> in the error message "<n> errors in database"

make that "what" is

In my case, I get "2 errors in the database". This didn't change when I removed my orphaned playlists.

Emptool makes no adverse comment.

grab http://64.83.11.163/jemplode/jemplode20.jar -- This has debug mode forced on and a slew of new debug printouts during the processing of the database. How do you run the app?

If you it via the executable, please edit jEmplode2.lax and look for the line that says "lax.stdout.redirect=status.txt" and change the "status.txt' part to a full path location of where you want the debug output to go. (/home/tms13/debug.txt or whatever). If you run it just with the java commandline, then just redirect output to a file.

Run jEmplode, select your Empeg, allow the database to parse, and go through the error correction then just quit out and email me the debug output (mschrag@cavtel.net)

Thanks a lot
Mike

Okay, lax.stdout.redirect=/dev/stdout .

The logfile is on its way to you.

i just download jemplode.jar a couple of minutes ago and when connecting to my player here at work (Windoze NT 4.0) it synced up and NOTHING showed up on the player.

I had renamed the previous pre-beta (2/25) I downloaded, so I replaced the jar file and everything showed up fine.

----

BTW That prebeta (2/25) gets hung up at the "Waiting for player to restart screen". Then JEmplode can not see it until I power cycle the player (though ping can see it).

It doesn't hang at home (Max OS 8.6), but home/work are slightly different versions.

OK -- someone else said this too -- I'm gonna yank this version because apparently it's not as much of a "fix" as I thought

Try the "new" one and see if it goes back to the way it used to work...

Just for grins -- try http://64.83.11.163/jemplode/jemplode20.jar